Task: Develop HW-SW verification plan
Development of the verification plan for the HW-SW integration level, describing the verification tools, methods and environment with pass and fail criteria.
Purpose

To describe the verification tools, methods and environment with pass and fail criteria to be applied at the HW-SW integration level.

Relationships
Main Description

ISO 26262, vol 8, clause 9 defines the guidance for generic aspects of verification planning which should be followed.

In order to detect systematic faults within the implementation of system design during the hardware-software integration various test methods must be selected that cover a variety of aspects of test and verification.

The selection of the application feasible methods are detailed in the step section.

Steps
Select methods for the correctness of implementation of system design specification and technical safety requirements

To ensure the technical safety requirements and correct implementation of the system design specification, certain test methods need to be applied. These are detailed in the table below, taken from ISO 26262 vol 4, clause 8.4.2.3.1.

          Correct implementation of technical safety requirements at the hardware-software level


This table/figure is taken from ISO 26262:2011-8.4.2.2.2 © ISO 2011 – All rights reserved. Reproduced with the permission of ANSI on behalf of ISO.

Copyright ISO 2011. All rights reserved. Reproduced with permission of ANSI.

Select methods for the correctness of functional performance of safety mechanisms (A) B, C, D

These tests are required for items of ASIL B, C or D and recommend for items of ASIL A

To ensure the correct functional performance of the safety mechanism, taking into account timing and accuracy the test methods detailed in the table below, taken from ISO 26262, vol 4, clause 8.4.2.3.2 shall be applied according the ASIL of the item under development.                     

Correct functional performance, accuracy and timing of safety mechanisms at the hardware-software level

This table/figure is taken from ISO 26262:2011-8.4.2.2.3 © ISO 2011 – All rights reserved. Reproduced with the permission of ANSI on behalf of ISO.

Copyright ISO 2011. All rights reserved. Reproduced with permission of ANSI.

Select methods for the consistency and correctness of implementation of external and internal interfaces (A) B, C, D

These tests are required for items of ASIL B, C or D and recommend for items of ASIL A

To ensure the consistency and correctness of the implementation of the internal and external interfaces, please refer to "Table 7-Consistent and correct implementation of external and internal interfaces at the HW-SW level" located at  ISO 26262, vol 4, clause 8.4.2.2.4. This table covers:-

Test of external interfaces

Test of internal interfaces

Interface consistency test

All these test methods are highly recommended for items of ASIL B,C or D and recommended for items of ASIL A

Interfaces tests of the test object include tests of analog and digital inputs and outputs, boundary tests and equivalent-class tests to completely test the specified interfaces, compatibility, timings and other specified ratings for the test object.

Internal interfaces of an ECU are tested by static tests for the compatibility of software and hardware as well as dynamic tests of SPI- or I2C-communications or any other interface between elements of an ECU.

Select methods for the effectiveness of diagnostic coverage of hardware fault detection mechanisms (A) (B), C, D

These tests are required for items of ASIL C or D and recommend for items of ASIL A or B

To ensure the effectiveness of the diagnostic coverage of the hardware fault detection, please refer to "Table 8- Effectiveness of safety mechanisms diagnostic coverage at the HW_SW level" located at ISO 26262, vol 4, clause 8.4.2.2.5. this table covers

Fault injection tests

Error Guessing

Both techniques are highly recommended for items of ASIL C or D and recommended for items of ASIL A or B

Fault injection introduces faults into the model at runtime to determine how the software reacts. This is normally achieved through a special test interface or hardware. This technique is often employed to improve test coverage of the safety requirements, this is because during normal operation safety mechanisms are not involved.

Error guessing employs expert knowledge and data collected from experience or the field. This is used to anticipate possible errors in the test object.

For references to fault models see ISO 26262 vol 5: , Annex D, Table D.1


Select methods for the level of robustness (A) (B), (C), D

These tests are required for items of ASIL D and recommend for items of ASIL A, B or C

The types of tests to ensure the level of robustness of the elements being tested are the following:

Resource usage tests

Stress tests

Both types of tests method are highly recommended for items of ASIL D and recommended for items of ASIL A ,B or C

Resource usage tests can be done statically or dynamically, for instance by checking code size, analyzing the interrupt usage in the code or monitoring the code dynamically at run time This helps to verify that the worst case scenarios do not run out of resources.

Stress tests are used to verify the correct operation of the item under high operational loads or extreme environmental conditions.

Please refer to "Table 9-Level of robustness", located in ISO 26262, vol 4, clause 8.4.2.2.6

Key Considerations

If the item is ASIL C or D then it is required to plan for the complete testing of the hardware software interface requirements at the HW-SW integration level. Otherwise a rationale will be provided that no remaining issue of the hardware software interface exists.

Practices applicable to help develop the HW- SW integration testing plan are

More Information